-
Notifications
You must be signed in to change notification settings - Fork 29.1k
[SPARK-33476][CORE] Generalize ExecutorSource to expose user-given file system schemes #30405
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Could you review this please, @viirya ? |
HyukjinKwon
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems OK to me.
viirya
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we need to update monitoring.md?
viirya
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks okay to me too.
|
Kubernetes integration test starting |
|
Thank you, @HyukjinKwon and @viirya . I'll mention this new conf in the |
| } | ||
| private val executorSource = new ExecutorSource(threadPool, executorId) | ||
| private val schemes = conf.get(EXECUTOR_METRICS_FILESYSTEM_SCHEMES) | ||
| .toLowerCase(Locale.ROOT).split(",").map(_.trim) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: filter empty after map ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, thanks, @mridulm !
|
Kubernetes integration test status success |
|
All comments are addressed. (@HyukjinKwon , @viirya , @mridulm ) |
|
Thank you, @viirya ! |
|
Test build #131259 has finished for PR 30405 at commit
|
|
Test build #131249 has finished for PR 30405 at commit
|
|
retest this please |
|
Kubernetes integration test starting |
|
Kubernetes integration test status success |
|
Kubernetes integration test starting |
|
Test build #131271 has finished for PR 30405 at commit
|
|
Kubernetes integration test status success |
|
Kubernetes integration test starting |
|
Kubernetes integration test status success |
|
Given the approvals, I'll merge this PR. |
What changes were proposed in this pull request?
This PR aims to generalize executor metrics to support user-given file system schemes instead of the fixed
file,hdfsscheme.Why are the changes needed?
For the users using only cloud storages like
S3A, we need to be able to exposeS3Ametrics. Also, we can skip unusedhdfsmetrics.Does this PR introduce any user-facing change?
Yes, but compatible for the existing users which uses
hdfsandfilefilesystem scheme only.How was this patch tested?
Manually do the following.
Separately, launch
jconsoleand check*.executor.filesystem.s3a.*. Also, confirm that there is no*.executor.filesystem.hdfs.*